Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5581f9ec492ea5e8a064c202e47a9ff59717c8abe21ba134d327668eb6a50c5

Tx prefix hash: cc9f093db2f16fcdf670074e2305cfcbd42480103ff8d5c9cbc08c80c59b0674
Tx public key: 7319df1b4b7b29b368c0b405f1dbf51ced1c4203ae5b667f441fd12eb63ad71f
Timestamp: 1705462914 Timestamp [UCT]: 2024-01-17 03:41:54 Age [y:d:h:m:s]: 01:120:01:25:56
Block: 937001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346933 RingCT/type: yes/0
Extra: 017319df1b4b7b29b368c0b405f1dbf51ced1c4203ae5b667f441fd12eb63ad71f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f49754fca2d9f4de22ea4b01a2c5ad0086af2e7470d3561047f1142b39ce6bed 0.600000000000 1395045 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": 937011, "vin": [ { "gen": { "height": 937001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f49754fca2d9f4de22ea4b01a2c5ad0086af2e7470d3561047f1142b39ce6bed" } } ], "extra": [ 1, 115, 25, 223, 27, 75, 123, 41, 179, 104, 192, 180, 5, 241, 219, 245, 28, 237, 28, 66, 3, 174, 91, 102, 127, 68, 31, 209, 46, 182, 58, 215, 31, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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