Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9f42aef9bfcc9bfa449d316378a54be991d55e41bb7aadc4f2d8b3808268b24

Tx prefix hash: 1ffa950a97f0e0e921c99f6a766bce1f7f4ce178c0a13bd10173701f9b087eea
Tx public key: c94677935285d1b113844f5df7c61b982bff76ea0b98134951d20be61ce073d9
Timestamp: 1735317081 Timestamp [UCT]: 2024-12-27 16:31:21 Age [y:d:h:m:s]: 00:316:18:00:21
Block: 1184408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223896 RingCT/type: yes/0
Extra: 01c94677935285d1b113844f5df7c61b982bff76ea0b98134951d20be61ce073d9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cda5b71a1db542abe90b10ccb5c1907bc478a115bbcadcd47508bea1e7fc5f3 0.600000000000 1670865 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": 1184418, "vin": [ { "gen": { "height": 1184408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cda5b71a1db542abe90b10ccb5c1907bc478a115bbcadcd47508bea1e7fc5f3" } } ], "extra": [ 1, 201, 70, 119, 147, 82, 133, 209, 177, 19, 132, 79, 93, 247, 198, 27, 152, 43, 255, 118, 234, 11, 152, 19, 73, 81, 210, 11, 230, 28, 224, 115, 217, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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