Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f01c8b43393b58f3f88c8d46778bcf39700bc6374a2dc47eb8ff0c9c385e678d

Tx prefix hash: 20e68d8d37c567cd328fc30c520415efb693aefc230fbe9535c04f5626c78258
Tx public key: dc1ae85e2f5d77e978011b74e494c020c2adafe674680ebcb1378ed4a49abbe9
Timestamp: 1703003661 Timestamp [UCT]: 2023-12-19 16:34:21 Age [y:d:h:m:s]: 01:043:00:41:26
Block: 916660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291833 RingCT/type: yes/0
Extra: 01dc1ae85e2f5d77e978011b74e494c020c2adafe674680ebcb1378ed4a49abbe9021100000004e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b035f2d2b76575158c40acc4210dc502ad7ca6e74d0ba6d7eff150a237ab45d6 0.600000000000 1374218 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": 916670, "vin": [ { "gen": { "height": 916660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b035f2d2b76575158c40acc4210dc502ad7ca6e74d0ba6d7eff150a237ab45d6" } } ], "extra": [ 1, 220, 26, 232, 94, 47, 93, 119, 233, 120, 1, 27, 116, 228, 148, 192, 32, 194, 173, 175, 230, 116, 104, 14, 188, 177, 55, 142, 212, 164, 154, 187, 233, 2, 17, 0, 0, 0, 4, 228, 187, 107, 131, 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