Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01c31805a664a46d62250cc62f2501aaa3697283091e3823e34f9f016de1ab0d

Tx prefix hash: e3ec2a0784d95d05703f6d2e70e90c313af32e75fd536f73f99a763ca071190b
Tx public key: 35990c8fee7b05f27a1e9ba5aabc9ed3e0cd9c725b0428be90e30e94d4b073d9
Timestamp: 1755057032 Timestamp [UCT]: 2025-08-13 03:50:32 Age [y:d:h:m:s]: 00:100:13:29:14
Block: 1345826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71264 RingCT/type: yes/0
Extra: 0135990c8fee7b05f27a1e9ba5aabc9ed3e0cd9c725b0428be90e30e94d4b073d9021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aee3013301a8345207a6cee0e14422319bd5cfc878f63264e6e5a8d346451bdd 0.600000000000 1833721 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": 1345836, "vin": [ { "gen": { "height": 1345826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aee3013301a8345207a6cee0e14422319bd5cfc878f63264e6e5a8d346451bdd" } } ], "extra": [ 1, 53, 153, 12, 143, 238, 123, 5, 242, 122, 30, 155, 165, 170, 188, 158, 211, 224, 205, 156, 114, 91, 4, 40, 190, 144, 227, 14, 148, 212, 176, 115, 217, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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