Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f2623e4855efc6af3a77a0571c8c47c2c0230b2511fd6b52e0254c0fdeb722e

Tx prefix hash: 37d8afbd338f34c32f682faf2af1d2843f6d3ca9a5db5f8c8115a569958871d6
Tx public key: 96d7641d02a1a0b9ae50ee0b90348a6d4bad79213ae9e57ca70a198ae21f65ba
Timestamp: 1744163189 Timestamp [UCT]: 2025-04-09 01:46:29 Age [y:d:h:m:s]: 00:298:10:47:42
Block: 1257374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210950 RingCT/type: yes/0
Extra: 0196d7641d02a1a0b9ae50ee0b90348a6d4bad79213ae9e57ca70a198ae21f65ba0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e81a9d7819fff957d32342e280247c0c2bf8cb475a83cd0fc1a3d65a3b9b77a 0.600000000000 1744495 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": 1257384, "vin": [ { "gen": { "height": 1257374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e81a9d7819fff957d32342e280247c0c2bf8cb475a83cd0fc1a3d65a3b9b77a" } } ], "extra": [ 1, 150, 215, 100, 29, 2, 161, 160, 185, 174, 80, 238, 11, 144, 52, 138, 109, 75, 173, 121, 33, 58, 233, 229, 124, 167, 10, 25, 138, 226, 31, 101, 186, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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