Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd9e8a622610d135987f028d0bb28c2231aad08c37d83de4826d89213e6e9a3c

Tx prefix hash: 1b5d6f86fb23347348f67ced282e6815fd985d55578c0013b81c4c2fff36ca93
Tx public key: 299c38b69b056cf8e953b1325f4e321b54188104bc306ed09920c9d2ea31b9bb
Timestamp: 1718827321 Timestamp [UCT]: 2024-06-19 20:02:01 Age [y:d:h:m:s]: 00:206:09:13:44
Block: 1047834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147686 RingCT/type: yes/0
Extra: 01299c38b69b056cf8e953b1325f4e321b54188104bc306ed09920c9d2ea31b9bb02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1129b6f759fae6874fd5ec5b1422cca7073eccf23e3b2418b07bef47c7c163b7 0.600000000000 1517761 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": 1047844, "vin": [ { "gen": { "height": 1047834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1129b6f759fae6874fd5ec5b1422cca7073eccf23e3b2418b07bef47c7c163b7" } } ], "extra": [ 1, 41, 156, 56, 182, 155, 5, 108, 248, 233, 83, 177, 50, 95, 78, 50, 27, 84, 24, 129, 4, 188, 48, 110, 208, 153, 32, 201, 210, 234, 49, 185, 187, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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