Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 013bd9403f1dd03fb1a1aa7e036026f11bf15bad12c138189bbcb94a88eb5518

Tx prefix hash: 040fd1f179c45a83df256e392df84c84f2f6a9ec7fe4e3e428c1cebdf2cc5bd1
Tx public key: 3896ef829e5b73c83ef5dd63b5fb47196abcbe0f72e786691857c07b06d8e150
Timestamp: 1735136962 Timestamp [UCT]: 2024-12-25 14:29:22 Age [y:d:h:m:s]: 00:090:13:27:29
Block: 1182935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64483 RingCT/type: yes/0
Extra: 013896ef829e5b73c83ef5dd63b5fb47196abcbe0f72e786691857c07b06d8e1500211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 473df206b329d23114e70f9acb51b38de817f105f13f61bf2d70be3d5ffda847 0.600000000000 1669374 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": 1182945, "vin": [ { "gen": { "height": 1182935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "473df206b329d23114e70f9acb51b38de817f105f13f61bf2d70be3d5ffda847" } } ], "extra": [ 1, 56, 150, 239, 130, 158, 91, 115, 200, 62, 245, 221, 99, 181, 251, 71, 25, 106, 188, 190, 15, 114, 231, 134, 105, 24, 87, 192, 123, 6, 216, 225, 80, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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