Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 313b8c4cc038226eb2f09534b2e5b0f10fc4ba10862b210c1e713fe00c34bb84

Tx prefix hash: d4787b663d2186557ce619f2d1de5837e78ca69fff9d530db63c151902fb46c3
Tx public key: 04a163571bd6a42a0128286f63ad5c1d5272fa04d47bc90a57230723a8562e2f
Timestamp: 1728570259 Timestamp [UCT]: 2024-10-10 14:24:19 Age [y:d:h:m:s]: 00:167:00:25:05
Block: 1128608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119132 RingCT/type: yes/0
Extra: 0104a163571bd6a42a0128286f63ad5c1d5272fa04d47bc90a57230723a8562e2f02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f858f976886a9dc68e2fea7e02545787fc76cd854a2b4a3ea4e47c0cb470f15 0.600000000000 1611427 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": 1128618, "vin": [ { "gen": { "height": 1128608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f858f976886a9dc68e2fea7e02545787fc76cd854a2b4a3ea4e47c0cb470f15" } } ], "extra": [ 1, 4, 161, 99, 87, 27, 214, 164, 42, 1, 40, 40, 111, 99, 173, 92, 29, 82, 114, 250, 4, 212, 123, 201, 10, 87, 35, 7, 35, 168, 86, 46, 47, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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