Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241768da1531bf93b8c09fc5356b19777dd02f625436b6e9fd8e8027d6e071ed

Tx prefix hash: 916e9a12484af94e461a65793c98751e8420bbb1d5d00632b6bd946abcc6eb83
Tx public key: dd994b85f4b5fd6808ac8c3ac2068b2a375d9ce903d48af919471b37fc52cdf9
Timestamp: 1751479770 Timestamp [UCT]: 2025-07-02 18:09:30 Age [y:d:h:m:s]: 00:130:03:55:45
Block: 1317385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91272 RingCT/type: yes/0
Extra: 01dd994b85f4b5fd6808ac8c3ac2068b2a375d9ce903d48af919471b37fc52cdf9021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9d175d82100ac7a0040420a327b374164d11536e030c41e1a118257d2ea44a2 0.600000000000 1805052 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": 1317395, "vin": [ { "gen": { "height": 1317385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d175d82100ac7a0040420a327b374164d11536e030c41e1a118257d2ea44a2" } } ], "extra": [ 1, 221, 153, 75, 133, 244, 181, 253, 104, 8, 172, 140, 58, 194, 6, 139, 42, 55, 93, 156, 233, 3, 212, 138, 249, 25, 71, 27, 55, 252, 82, 205, 249, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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