Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 617dc769cbd2130049c9ff8af77c45261534f3daf1f59997977a2dd0ec51888d

Tx prefix hash: 434a8c13a309572897a443644e824adfd30fae2372c4ddd956ca0004df8920d4
Tx public key: a7edfa2dd40423b0d5b4e16495a3ac9d94f657c72ba9417ad183312d91100c4d
Timestamp: 1732648372 Timestamp [UCT]: 2024-11-26 19:12:52 Age [y:d:h:m:s]: 00:206:12:41:26
Block: 1162315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147296 RingCT/type: yes/0
Extra: 01a7edfa2dd40423b0d5b4e16495a3ac9d94f657c72ba9417ad183312d91100c4d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ffcf5e02c2d871c3065be4d59a757336292ef8fd8c55a189ff6f3041bf26c1f 0.600000000000 1647970 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": 1162325, "vin": [ { "gen": { "height": 1162315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ffcf5e02c2d871c3065be4d59a757336292ef8fd8c55a189ff6f3041bf26c1f" } } ], "extra": [ 1, 167, 237, 250, 45, 212, 4, 35, 176, 213, 180, 225, 100, 149, 163, 172, 157, 148, 246, 87, 199, 43, 169, 65, 122, 209, 131, 49, 45, 145, 16, 12, 77, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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