Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 805f22805a5b55ecb3fe4d5b0be1cd4a40c3bc3efd77a92fa060a7659689b370

Tx prefix hash: 5e3cf511303b15cd84da270612f121ddc01a69e43cc44f8327dea484a1124acd
Tx public key: 56e86e6e970df01f5919a13150143adfeab1084c75c8ae8e3a015ee7550155a6
Timestamp: 1740921693 Timestamp [UCT]: 2025-03-02 13:21:33 Age [y:d:h:m:s]: 00:256:21:24:49
Block: 1230537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181356 RingCT/type: yes/0
Extra: 0156e86e6e970df01f5919a13150143adfeab1084c75c8ae8e3a015ee7550155a60211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2512a1d6a0de8097b0f8545e16b1af0d9f4f4c90a55fa89224484d9027e2f72 0.600000000000 1717436 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": 1230547, "vin": [ { "gen": { "height": 1230537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2512a1d6a0de8097b0f8545e16b1af0d9f4f4c90a55fa89224484d9027e2f72" } } ], "extra": [ 1, 86, 232, 110, 110, 151, 13, 240, 31, 89, 25, 161, 49, 80, 20, 58, 223, 234, 177, 8, 76, 117, 200, 174, 142, 58, 1, 94, 231, 85, 1, 85, 166, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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