Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed3f300a71769e8067b446155cc907854fb9b8919af8da44c608cf1504ea945

Tx prefix hash: c872c77482e507ab34d603a67c4902bfd2811f7f016c38b1d3430948788f209e
Tx public key: f846e0859dbea992c0bbcf8dc4ac41b1fe5b0f0c1dbae07503e81d20bc2bfd14
Timestamp: 1703523870 Timestamp [UCT]: 2023-12-25 17:04:30 Age [y:d:h:m:s]: 01:016:11:41:54
Block: 920966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273110 RingCT/type: yes/0
Extra: 01f846e0859dbea992c0bbcf8dc4ac41b1fe5b0f0c1dbae07503e81d20bc2bfd1402110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 165b5358455be4b8389136aa74173aa22165de70374538013b91b18e6e009894 0.600000000000 1378650 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": 920976, "vin": [ { "gen": { "height": 920966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "165b5358455be4b8389136aa74173aa22165de70374538013b91b18e6e009894" } } ], "extra": [ 1, 248, 70, 224, 133, 157, 190, 169, 146, 192, 187, 207, 141, 196, 172, 65, 177, 254, 91, 15, 12, 29, 186, 224, 117, 3, 232, 29, 32, 188, 43, 253, 20, 2, 17, 0, 0, 0, 19, 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