Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379af9af33cea138dbf7473af2aefdca759b96ccffb38d3ce4101445b548fbb6

Tx prefix hash: 3dbc523ba72129a0a4438a5be4be79689546ae64bf43bdc41ac934e3fdd057c3
Tx public key: d0f8c515c5f027eda92adb01f0a8a6342bfdea8bb815f7fcfca15fd4c330d8d7
Timestamp: 1630039251 Timestamp [UCT]: 2021-08-27 04:40:51 Age [y:d:h:m:s]: 03:259:07:21:52
Block: 321605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 959688 RingCT/type: yes/0
Extra: 01d0f8c515c5f027eda92adb01f0a8a6342bfdea8bb815f7fcfca15fd4c330d8d702110000002248397882000000000000000000

1 output(s) for total of 52.770303171000 dcy

stealth address amount amount idx
00: 7244d18e3f9ae0e34336fcdbc0de48fd548cff43500d95f3f3182b09f4f95b16 52.770303171000 667579 of 0

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": 321615, "vin": [ { "gen": { "height": 321605 } } ], "vout": [ { "amount": 52770303171, "target": { "key": "7244d18e3f9ae0e34336fcdbc0de48fd548cff43500d95f3f3182b09f4f95b16" } } ], "extra": [ 1, 208, 248, 197, 21, 197, 240, 39, 237, 169, 42, 219, 1, 240, 168, 166, 52, 43, 253, 234, 139, 184, 21, 247, 252, 252, 161, 95, 212, 195, 48, 216, 215, 2, 17, 0, 0, 0, 34, 72, 57, 120, 130, 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