Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da61eb405c0c1f1992d3452ae67edff9edf847fe0e3942a51303581803828f1

Tx prefix hash: ae11aaef17674016f03fea2eacf4744b532c809a591a62c41044cf66d9999e87
Tx public key: 17c8a2e62064230df0be9779953e5b5c3291a962f241db108591db1590e1e825
Timestamp: 1729628101 Timestamp [UCT]: 2024-10-22 20:15:01 Age [y:d:h:m:s]: 00:067:20:15:46
Block: 1137349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48488 RingCT/type: yes/0
Extra: 0117c8a2e62064230df0be9779953e5b5c3291a962f241db108591db1590e1e82502110000000192627dee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a22dcd2b07bb6726af9d4ee2798df15df12e9b05fb4e248f08a3ba0655ea885 0.600000000000 1620822 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": 1137359, "vin": [ { "gen": { "height": 1137349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a22dcd2b07bb6726af9d4ee2798df15df12e9b05fb4e248f08a3ba0655ea885" } } ], "extra": [ 1, 23, 200, 162, 230, 32, 100, 35, 13, 240, 190, 151, 121, 149, 62, 91, 92, 50, 145, 169, 98, 242, 65, 219, 16, 133, 145, 219, 21, 144, 225, 232, 37, 2, 17, 0, 0, 0, 1, 146, 98, 125, 238, 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