Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79b4d823a24172a7ed53b35401ecebc4908505f8e9058839e3f7af2e33b09d8f

Tx prefix hash: 9ff9df160e3532b46ffb2a06fa2d3bd041c61ffd41519515ea173c17ad6920c2
Tx public key: 93e51779db8b503564496311a68c4156a51ec846d4bfdc0909af5a174f07e2bd
Timestamp: 1733584581 Timestamp [UCT]: 2024-12-07 15:16:21 Age [y:d:h:m:s]: 00:348:10:47:37
Block: 1170076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246558 RingCT/type: yes/0
Extra: 0193e51779db8b503564496311a68c4156a51ec846d4bfdc0909af5a174f07e2bd021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f242f3a71e1b5a6a07344147877b6e99872a54dd3b6dc8171325d3e447b4423 0.600000000000 1655805 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": 1170086, "vin": [ { "gen": { "height": 1170076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f242f3a71e1b5a6a07344147877b6e99872a54dd3b6dc8171325d3e447b4423" } } ], "extra": [ 1, 147, 229, 23, 121, 219, 139, 80, 53, 100, 73, 99, 17, 166, 140, 65, 86, 165, 30, 200, 70, 212, 191, 220, 9, 9, 175, 90, 23, 79, 7, 226, 189, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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