Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c15e443cfd5e3ee28362dd4b6428d6fca6f2e64b21a1bf8ee9a54bca84d507c4

Tx prefix hash: 4b6bc84a9301c5c474ecd089b38aa4fdf969194cc53ed61c3e5e2a7876941697
Tx public key: 8497e5148aa41d07cc83b5ee94859a0e7dc5ca58df1247a91fd114c4a3a72f3a
Timestamp: 1737108328 Timestamp [UCT]: 2025-01-17 10:05:28 Age [y:d:h:m:s]: 00:152:13:54:44
Block: 1199245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108734 RingCT/type: yes/0
Extra: 018497e5148aa41d07cc83b5ee94859a0e7dc5ca58df1247a91fd114c4a3a72f3a021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 476d6ce183eb6856a7274f5eb5218bd1d96bdd73859ce7b87cf3baa6c415c6ed 0.600000000000 1685874 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": 1199255, "vin": [ { "gen": { "height": 1199245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "476d6ce183eb6856a7274f5eb5218bd1d96bdd73859ce7b87cf3baa6c415c6ed" } } ], "extra": [ 1, 132, 151, 229, 20, 138, 164, 29, 7, 204, 131, 181, 238, 148, 133, 154, 14, 125, 197, 202, 88, 223, 18, 71, 169, 31, 209, 20, 196, 163, 167, 47, 58, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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