Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6d805920810c5399f130f771839117da7ad64614fa150b6599a3d8bab3be03

Tx prefix hash: 1ce6a8eafe18bd4420da72f8c9b99f1ae2bfc9319be68c55cfa701e038ffc6e1
Tx public key: e340e757605b99ab246d5639cd35d4107f04f48a8003b2616edfc2a7c2e170e0
Timestamp: 1733587554 Timestamp [UCT]: 2024-12-07 16:05:54 Age [y:d:h:m:s]: 00:107:23:03:40
Block: 1170100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76945 RingCT/type: yes/0
Extra: 01e340e757605b99ab246d5639cd35d4107f04f48a8003b2616edfc2a7c2e170e002110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c8fdb9d7cddd12e5d2da6ecc3daa5e94cb48dec10e37db8200d2f0d95efd286 0.600000000000 1655829 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": 1170110, "vin": [ { "gen": { "height": 1170100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c8fdb9d7cddd12e5d2da6ecc3daa5e94cb48dec10e37db8200d2f0d95efd286" } } ], "extra": [ 1, 227, 64, 231, 87, 96, 91, 153, 171, 36, 109, 86, 57, 205, 53, 212, 16, 127, 4, 244, 138, 128, 3, 178, 97, 110, 223, 194, 167, 194, 225, 112, 224, 2, 17, 0, 0, 0, 11, 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