Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c94c4497f35332095a97f92abe1bdde8a7844cde93bf76f61e1869a9bc514999

Tx prefix hash: 73ff09893fd5c7c2e6c4e501c151be47d4d5f17c4074b98c261b682db7ba609c
Tx public key: aa4d400dfce6c1e3e0522c1a25b15dfe07bd6245ebcc46b69725da3656eb8251
Timestamp: 1720426920 Timestamp [UCT]: 2024-07-08 08:22:00 Age [y:d:h:m:s]: 00:346:14:23:55
Block: 1061102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247548 RingCT/type: yes/0
Extra: 01aa4d400dfce6c1e3e0522c1a25b15dfe07bd6245ebcc46b69725da3656eb8251021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91916c717d4b21d5ced017fe8f2aa3252e9bd19e035fbd739266e08e3c94abca 0.600000000000 1531593 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": 1061112, "vin": [ { "gen": { "height": 1061102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91916c717d4b21d5ced017fe8f2aa3252e9bd19e035fbd739266e08e3c94abca" } } ], "extra": [ 1, 170, 77, 64, 13, 252, 230, 193, 227, 224, 82, 44, 26, 37, 177, 93, 254, 7, 189, 98, 69, 235, 204, 70, 182, 151, 37, 218, 54, 86, 235, 130, 81, 2, 17, 0, 0, 0, 8, 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