Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4fbae53ed57d24a060c3c26277d592a978f8e6144da35dc22477272bcd0abfa0

Tx prefix hash: 34ac8bd4ab1327c16992bf10aefdc1d6b00005cb38e47ecb9d70692c5e144eec
Tx public key: 32b9e784e7297e02950c61f2054f13a7f7f51edbfd45ec0fb7517c7800b9eb1e
Timestamp: 1749527742 Timestamp [UCT]: 2025-06-10 03:55:42 Age [y:d:h:m:s]: 00:162:22:19:42
Block: 1301810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114127 RingCT/type: yes/0
Extra: 0132b9e784e7297e02950c61f2054f13a7f7f51edbfd45ec0fb7517c7800b9eb1e021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0ee88f7582512d6346fcd8e78bfefbed79c7b43a115fe4c1246b271e744e462 0.600000000000 1789371 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1301820, "vin": [ { "gen": { "height": 1301810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0ee88f7582512d6346fcd8e78bfefbed79c7b43a115fe4c1246b271e744e462" } } ], "extra": [ 1, 50, 185, 231, 132, 231, 41, 126, 2, 149, 12, 97, 242, 5, 79, 19, 167, 247, 245, 30, 219, 253, 69, 236, 15, 183, 81, 124, 120, 0, 185, 235, 30, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8