Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dbdb81ffa13b90ddcf1ad4732d5df752ea8758e41cb64b1fa24ece6559307c4

Tx prefix hash: 05526d6e4a14055d32e9c537bbbf773a77a6c3d1f5ef7e566e07c1bfde9b8013
Tx public key: 5d674931b5ed66c450cf559f575d5e0e3d2a486dd04cd3baa4295bbb93f15938
Timestamp: 1745721715 Timestamp [UCT]: 2025-04-27 02:41:55 Age [y:d:h:m:s]: 00:274:01:31:13
Block: 1270288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193498 RingCT/type: yes/0
Extra: 015d674931b5ed66c450cf559f575d5e0e3d2a486dd04cd3baa4295bbb93f15938021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5df2b59a32e9b46d26322d26ab1617b82534d5ce0403ed415998b0ae2c8eee08 0.600000000000 1757529 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": 1270298, "vin": [ { "gen": { "height": 1270288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5df2b59a32e9b46d26322d26ab1617b82534d5ce0403ed415998b0ae2c8eee08" } } ], "extra": [ 1, 93, 103, 73, 49, 181, 237, 102, 196, 80, 207, 85, 159, 87, 93, 94, 14, 61, 42, 72, 109, 208, 76, 211, 186, 164, 41, 91, 187, 147, 241, 89, 56, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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