Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f30b9c1e401c1318d0db53b36f29f8c317bc0979cb15b75d525163ec53d90714

Tx prefix hash: bbd323feea3d3259ed1d4b08c7c2050d4ad70af12c20b56b1c6ddb705e470baa
Tx public key: 6c4e49b8120c0efe20280b9bc389323dadfa10bfd7d8471a58e4d11b81523727
Timestamp: 1715907723 Timestamp [UCT]: 2024-05-17 01:02:03 Age [y:d:h:m:s]: 00:238:07:37:40
Block: 1023630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170563 RingCT/type: yes/0
Extra: 016c4e49b8120c0efe20280b9bc389323dadfa10bfd7d8471a58e4d11b8152372702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ef914e5b0e28ba74744a4e69efbfedd3234e224b2f904bd213709643509c625 0.600000000000 1488749 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": 1023640, "vin": [ { "gen": { "height": 1023630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ef914e5b0e28ba74744a4e69efbfedd3234e224b2f904bd213709643509c625" } } ], "extra": [ 1, 108, 78, 73, 184, 18, 12, 14, 254, 32, 40, 11, 155, 195, 137, 50, 61, 173, 250, 16, 191, 215, 216, 71, 26, 88, 228, 209, 27, 129, 82, 55, 39, 2, 17, 0, 0, 0, 1, 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