Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdb68d5f2438e2040a18b49026e38be8bcf0940db1bd029861d7769b25ebbe63

Tx prefix hash: 5641b0ea8b1d7a0a31ccea9d3fe573101c11bb79f130e716a71dcfe4a2ce952f
Tx public key: 6cc94896a3f76db109c460fe85d18621e08ee5def01b81fd64cc6b2353cca4b1
Timestamp: 1752608476 Timestamp [UCT]: 2025-07-15 19:41:16 Age [y:d:h:m:s]: 00:122:04:24:26
Block: 1326228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86061 RingCT/type: yes/0
Extra: 016cc94896a3f76db109c460fe85d18621e08ee5def01b81fd64cc6b2353cca4b1021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdb0e85e82744bd7fa1156fdccc7a7b1929e6cff26c15a64757e85d4633efa27 0.600000000000 1813979 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": 1326238, "vin": [ { "gen": { "height": 1326228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdb0e85e82744bd7fa1156fdccc7a7b1929e6cff26c15a64757e85d4633efa27" } } ], "extra": [ 1, 108, 201, 72, 150, 163, 247, 109, 177, 9, 196, 96, 254, 133, 209, 134, 33, 224, 142, 229, 222, 240, 27, 129, 253, 100, 204, 107, 35, 83, 204, 164, 177, 2, 17, 0, 0, 0, 4, 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