Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a48f55de52a907363c921078ee83cd87b7663fc9fa9f1e5da4b1b4e1aeabf8a

Tx prefix hash: 41c0a45ac988a2efa7bdc2c53699010c8eadea28865b0ff7139cb41bccb082f0
Tx public key: cf4a174a10f213a095dfbe5a61d3671a5574f0fcb4eae0dd3fafd901c219408a
Timestamp: 1761593807 Timestamp [UCT]: 2025-10-27 19:36:47 Age [y:d:h:m:s]: 00:012:05:20:09
Block: 1399276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8740 RingCT/type: yes/0
Extra: 01cf4a174a10f213a095dfbe5a61d3671a5574f0fcb4eae0dd3fafd901c219408a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2b2be0a7c245c76c7ba7dfecd1d535e64f1399b6368e00b3b4734713955c384 0.600000000000 1887581 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": 1399286, "vin": [ { "gen": { "height": 1399276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2b2be0a7c245c76c7ba7dfecd1d535e64f1399b6368e00b3b4734713955c384" } } ], "extra": [ 1, 207, 74, 23, 74, 16, 242, 19, 160, 149, 223, 190, 90, 97, 211, 103, 26, 85, 116, 240, 252, 180, 234, 224, 221, 63, 175, 217, 1, 194, 25, 64, 138, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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