Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1a4b1d770cc959149920280d8ca85ef39a1dbca49b63966ce61d7e04e3a57e2

Tx prefix hash: 0db3b04379922927f1d7c1e5a9fa8c880a3843ca91c61708234b722a78397a14
Tx public key: fac52938bee11cd5b6a24e9ca4c4ab39e767f246eae76206375795f36cb6afc0
Timestamp: 1728996725 Timestamp [UCT]: 2024-10-15 12:52:05 Age [y:d:h:m:s]: 00:099:11:15:03
Block: 1132147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71050 RingCT/type: yes/0
Extra: 01fac52938bee11cd5b6a24e9ca4c4ab39e767f246eae76206375795f36cb6afc0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4f2b4ad89ffd2d8e9991aa8432bd722abffea947d1e180af09ec739b8e37f0f 0.600000000000 1615060 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": 1132157, "vin": [ { "gen": { "height": 1132147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f2b4ad89ffd2d8e9991aa8432bd722abffea947d1e180af09ec739b8e37f0f" } } ], "extra": [ 1, 250, 197, 41, 56, 190, 225, 28, 213, 182, 162, 78, 156, 164, 196, 171, 57, 231, 103, 242, 70, 234, 231, 98, 6, 55, 87, 149, 243, 108, 182, 175, 192, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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