Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4641000d4b36e630101c76f01555a1ad3b0fcea79f518d1760a73a743ddeaa61

Tx prefix hash: e50e2c36722cc2599770aaa95261f0f9d4eb9a6f70a9eb5930e5c638a198e740
Tx public key: 135ec3fb3336d9bfba39f0f2dbf4e9cf6a22ea0b1bb3950aaecdb62e64ef4710
Timestamp: 1724065843 Timestamp [UCT]: 2024-08-19 11:10:43 Age [y:d:h:m:s]: 00:233:07:18:24
Block: 1091262 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166613 RingCT/type: yes/0
Extra: 01135ec3fb3336d9bfba39f0f2dbf4e9cf6a22ea0b1bb3950aaecdb62e64ef4710021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f71ca358a3f20c283f36cdcbe5778589d02d9386538771a4302f83daa4502c5a 0.600000000000 1565893 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": 1091272, "vin": [ { "gen": { "height": 1091262 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f71ca358a3f20c283f36cdcbe5778589d02d9386538771a4302f83daa4502c5a" } } ], "extra": [ 1, 19, 94, 195, 251, 51, 54, 217, 191, 186, 57, 240, 242, 219, 244, 233, 207, 106, 34, 234, 11, 27, 179, 149, 10, 174, 205, 182, 46, 100, 239, 71, 16, 2, 17, 0, 0, 0, 2, 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