Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a171b67cd402e38afbdc4dd151920ee1c74718fa545e416c4d8a20ea2ad89e2b

Tx prefix hash: 5dd1e418c416a763eb9cfeac3ef7c816eaa24348e57253d967cd5c3552f79b67
Tx public key: 858492d77771de17254e734c92dc856711a11e8abbfd51532aa7b5250c0d9528
Timestamp: 1754444130 Timestamp [UCT]: 2025-08-06 01:35:30 Age [y:d:h:m:s]: 00:014:17:55:22
Block: 1341160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9622 RingCT/type: yes/0
Extra: 01858492d77771de17254e734c92dc856711a11e8abbfd51532aa7b5250c0d95280211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0178f0d9c2123d92ea5b450ca45aa2a7a3e1a65103de8929efd153caae823dc3 0.600000000000 1828983 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": 1341170, "vin": [ { "gen": { "height": 1341160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0178f0d9c2123d92ea5b450ca45aa2a7a3e1a65103de8929efd153caae823dc3" } } ], "extra": [ 1, 133, 132, 146, 215, 119, 113, 222, 23, 37, 78, 115, 76, 146, 220, 133, 103, 17, 161, 30, 138, 187, 253, 81, 83, 42, 167, 181, 37, 12, 13, 149, 40, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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