Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5da927d6538f10de713ae2f2d15f4bcd221c13a288e50b98114a86d18feef638

Tx prefix hash: 6bf06f9708b2b1517051dd8403ea5d5ddb901fd33cef14e5f291f6478659ecc6
Tx public key: d56baba1be6af7e3b642b6019dae47b1e25bd1ad3c00e44f3980133da928b615
Timestamp: 1703860682 Timestamp [UCT]: 2023-12-29 14:38:02 Age [y:d:h:m:s]: 01:341:23:51:06
Block: 923749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503278 RingCT/type: yes/0
Extra: 01d56baba1be6af7e3b642b6019dae47b1e25bd1ad3c00e44f3980133da928b61502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aebdf86e30d42db1c87a221575a5b836d9fb059db11aa07e6d2b6ba440478446 0.600000000000 1381485 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": 923759, "vin": [ { "gen": { "height": 923749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aebdf86e30d42db1c87a221575a5b836d9fb059db11aa07e6d2b6ba440478446" } } ], "extra": [ 1, 213, 107, 171, 161, 190, 106, 247, 227, 182, 66, 182, 1, 157, 174, 71, 177, 226, 91, 209, 173, 60, 0, 228, 79, 57, 128, 19, 61, 169, 40, 182, 21, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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