Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f60ffabc3ab14cc3d1d2f191c8041449a297b16cb716483b04a9c43bc839802

Tx prefix hash: 092f5bb697e432ce362dce9e09e798d4414c27e47ad493ff0501536b9b869bcb
Tx public key: 983dcd1ba004a4208ceb8e1c84e51922aeecf53be9e7345cddd15da06cb6639a
Timestamp: 1715891328 Timestamp [UCT]: 2024-05-16 20:28:48 Age [y:d:h:m:s]: 00:329:05:25:12
Block: 1023497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235318 RingCT/type: yes/0
Extra: 01983dcd1ba004a4208ceb8e1c84e51922aeecf53be9e7345cddd15da06cb6639a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cb94b894b1a06f42e5ac6fb4f0046a69e6d4a41980877890b9e7c0417acb221 0.600000000000 1488514 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": 1023507, "vin": [ { "gen": { "height": 1023497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cb94b894b1a06f42e5ac6fb4f0046a69e6d4a41980877890b9e7c0417acb221" } } ], "extra": [ 1, 152, 61, 205, 27, 160, 4, 164, 32, 140, 235, 142, 28, 132, 229, 25, 34, 174, 236, 245, 59, 233, 231, 52, 92, 221, 209, 93, 160, 108, 182, 99, 154, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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