Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ae9a4f3a4875d4f4dd91095590ae92acaedd2755a40142e8d74f88fa736f31a

Tx prefix hash: 372c3638f082dfba4d13474508bdd8439c15dad55c0c47c5d3a68f3313856872
Tx public key: ac01cbcd5bbefaf8dcb8ff8a3b1d688e89e433a904da90873c2cf2fc336183c6
Timestamp: 1703127907 Timestamp [UCT]: 2023-12-21 03:05:07 Age [y:d:h:m:s]: 01:144:12:01:19
Block: 917699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364400 RingCT/type: yes/0
Extra: 01ac01cbcd5bbefaf8dcb8ff8a3b1d688e89e433a904da90873c2cf2fc336183c6021100000003679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1448fede381910464378db552dec26893e7e5edc40f6c44c888c7eafe03b6aa 0.600000000000 1375281 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": 917709, "vin": [ { "gen": { "height": 917699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1448fede381910464378db552dec26893e7e5edc40f6c44c888c7eafe03b6aa" } } ], "extra": [ 1, 172, 1, 203, 205, 91, 190, 250, 248, 220, 184, 255, 138, 59, 29, 104, 142, 137, 228, 51, 169, 4, 218, 144, 135, 60, 44, 242, 252, 51, 97, 131, 198, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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