Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfcfd3ff13cf85e4ff85aeb8747232a8bbc5d47a32e9ebfdf181d33d16712872

Tx prefix hash: ffbe2d78f88042f82dc8edc328a28b9446bc927057170fc69223546dc691d7d5
Tx public key: 97fab907e32f58c1ab2c31ad6cae1a97a855be68b6fdcf564de1894c088d4054
Timestamp: 1755456532 Timestamp [UCT]: 2025-08-17 18:48:52 Age [y:d:h:m:s]: 00:095:07:49:36
Block: 1348676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67972 RingCT/type: yes/0
Extra: 0197fab907e32f58c1ab2c31ad6cae1a97a855be68b6fdcf564de1894c088d4054021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9d1746259262981d5e59d161f3c19af78a874bcf2c20436f5ee29c2a7ac9b49 0.600000000000 1836603 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": 1348686, "vin": [ { "gen": { "height": 1348676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9d1746259262981d5e59d161f3c19af78a874bcf2c20436f5ee29c2a7ac9b49" } } ], "extra": [ 1, 151, 250, 185, 7, 227, 47, 88, 193, 171, 44, 49, 173, 108, 174, 26, 151, 168, 85, 190, 104, 182, 253, 207, 86, 77, 225, 137, 76, 8, 141, 64, 84, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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