Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24d64031020674fa135ac0e3ee4d93ec7e7072429efd10a4a8bbb24c5d0b81b0

Tx prefix hash: ba1a349aaa97811bc1931f53a68eb1c530c96ae3d2032f77e659996c150b2eea
Tx public key: a55d483814f9966620463f29c9d71cb819c2e972d5984d4fc449b6f97a54e5a1
Timestamp: 1717082016 Timestamp [UCT]: 2024-05-30 15:13:36 Age [y:d:h:m:s]: 00:299:15:07:17
Block: 1033363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214126 RingCT/type: yes/0
Extra: 01a55d483814f9966620463f29c9d71cb819c2e972d5984d4fc449b6f97a54e5a102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42be249be66600311c336f1de4afcea2bf4bcf481f974b1b908f7b138211fb48 0.600000000000 1501828 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": 1033373, "vin": [ { "gen": { "height": 1033363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42be249be66600311c336f1de4afcea2bf4bcf481f974b1b908f7b138211fb48" } } ], "extra": [ 1, 165, 93, 72, 56, 20, 249, 150, 102, 32, 70, 63, 41, 201, 215, 28, 184, 25, 194, 233, 114, 213, 152, 77, 79, 196, 73, 182, 249, 122, 84, 229, 161, 2, 17, 0, 0, 0, 2, 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