Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1ab603be111a2de2bdcb60f181bb8bb4c4600de2eb5815971ad51256a0c1e0a

Tx prefix hash: 106efccc5d157d518fd1ff4b54ca06028dae69155549a7b78a9a4a4b4cf04341
Tx public key: e3e9c6249642ea7c30d08fba4bd82ba6d0c94ba13655192bbd7b334f6755b402
Timestamp: 1721490075 Timestamp [UCT]: 2024-07-20 15:41:15 Age [y:d:h:m:s]: 00:299:13:07:53
Block: 1069904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214029 RingCT/type: yes/0
Extra: 01e3e9c6249642ea7c30d08fba4bd82ba6d0c94ba13655192bbd7b334f6755b402021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2d05fa956c1c2f58e310bf8b3c32ed1d367063d59586b3996ce5245a09fabd9 0.600000000000 1541521 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": 1069914, "vin": [ { "gen": { "height": 1069904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2d05fa956c1c2f58e310bf8b3c32ed1d367063d59586b3996ce5245a09fabd9" } } ], "extra": [ 1, 227, 233, 198, 36, 150, 66, 234, 124, 48, 208, 143, 186, 75, 216, 43, 166, 208, 201, 75, 161, 54, 85, 25, 43, 189, 123, 51, 79, 103, 85, 180, 2, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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