Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4986ef57818eb6a89328cde4de95a273586911fb694bf88571a7ad6303a07d0e

Tx prefix hash: e28eb0336cfb66e19bcfb56830a0ef79e913b8245ca508c226836912193b0508
Tx public key: a71e4ae0e4bfa43cbd7237bcce2b04b4a90e5a7f3a774d31f03b4530b5bd0b8e
Timestamp: 1704184188 Timestamp [UCT]: 2024-01-02 08:29:48 Age [y:d:h:m:s]: 01:072:07:07:29
Block: 926427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312790 RingCT/type: yes/0
Extra: 01a71e4ae0e4bfa43cbd7237bcce2b04b4a90e5a7f3a774d31f03b4530b5bd0b8e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 296882ad96946eb6b67836aced3a590caaaab4ed34f25b9002cc8c6f5f1334de 0.600000000000 1384211 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": 926437, "vin": [ { "gen": { "height": 926427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "296882ad96946eb6b67836aced3a590caaaab4ed34f25b9002cc8c6f5f1334de" } } ], "extra": [ 1, 167, 30, 74, 224, 228, 191, 164, 60, 189, 114, 55, 188, 206, 43, 4, 180, 169, 14, 90, 127, 58, 119, 77, 49, 240, 59, 69, 48, 181, 189, 11, 142, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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