Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47f6fe49fb39777950cab639f56b0b25c15f244208df7a20ab3bfb27f376a8d8

Tx prefix hash: d427c6e6e8fca1353f424b8664826fe39ef9867b2de6f71e3b5b974cb45703aa
Tx public key: 10477b584cd4722e4a069a6edbc21bfc7aeee66730ff31a05d87428a14804745
Timestamp: 1720945453 Timestamp [UCT]: 2024-07-14 08:24:13 Age [y:d:h:m:s]: 00:223:03:30:57
Block: 1065408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159350 RingCT/type: yes/0
Extra: 0110477b584cd4722e4a069a6edbc21bfc7aeee66730ff31a05d87428a1480474502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a2a8acfd1ee72d449cd3c2af05d596e904c991244fa147a2a73baa53f248f7 0.600000000000 1535953 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": 1065418, "vin": [ { "gen": { "height": 1065408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a2a8acfd1ee72d449cd3c2af05d596e904c991244fa147a2a73baa53f248f7" } } ], "extra": [ 1, 16, 71, 123, 88, 76, 212, 114, 46, 74, 6, 154, 110, 219, 194, 27, 252, 122, 238, 230, 103, 48, 255, 49, 160, 93, 135, 66, 138, 20, 128, 71, 69, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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