Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1adadb6e125870e046a6ba9a4219396fca235f702bb4c5a2f570cde698016baa

Tx prefix hash: cd7db3db2071aa5e2c080c685d1dc2832d95e533554bae27b6eb9871ed66fb06
Tx public key: 7b1b6e12b9aa6385fc39068cd214f3b28fe410465249dbf4556d0c5ba418c2b2
Timestamp: 1702446854 Timestamp [UCT]: 2023-12-13 05:54:14 Age [y:d:h:m:s]: 01:039:13:02:58
Block: 912050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289564 RingCT/type: yes/0
Extra: 017b1b6e12b9aa6385fc39068cd214f3b28fe410465249dbf4556d0c5ba418c2b202110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2633b47ac66c0de10da2e4dd43c0474be96980b7a8f86ca6da07e2b913453ec 0.600000000000 1369268 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": 912060, "vin": [ { "gen": { "height": 912050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2633b47ac66c0de10da2e4dd43c0474be96980b7a8f86ca6da07e2b913453ec" } } ], "extra": [ 1, 123, 27, 110, 18, 185, 170, 99, 133, 252, 57, 6, 140, 210, 20, 243, 178, 143, 228, 16, 70, 82, 73, 219, 244, 85, 109, 12, 91, 164, 24, 194, 178, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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