Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f88cda1638b23ee93394d5a9a3448811cc0ab42a0419dfa860d2dca678875b7c

Tx prefix hash: bf9d446339a01e80356d634b1a45ca560a1eacb753241e2aae697fb087565637
Tx public key: 5cbd61ac3d6b2b0e454729773b0523f86e64dbd836ddf3b3dd50b0884b501da8
Timestamp: 1709951901 Timestamp [UCT]: 2024-03-09 02:38:21 Age [y:d:h:m:s]: 01:213:23:45:12
Block: 974259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411607 RingCT/type: yes/0
Extra: 015cbd61ac3d6b2b0e454729773b0523f86e64dbd836ddf3b3dd50b0884b501da802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26beb5a63b2ffabfba306f0b83b8cb79022c1b26b48c5b61f0e4394515f18fdf 0.600000000000 1434214 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": 974269, "vin": [ { "gen": { "height": 974259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26beb5a63b2ffabfba306f0b83b8cb79022c1b26b48c5b61f0e4394515f18fdf" } } ], "extra": [ 1, 92, 189, 97, 172, 61, 107, 43, 14, 69, 71, 41, 119, 59, 5, 35, 248, 110, 100, 219, 216, 54, 221, 243, 179, 221, 80, 176, 136, 75, 80, 29, 168, 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