Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36ebece2b27ce1ee8142797d130055cfd0221ffa05cd81708f6a0f7060350232

Tx prefix hash: 8f49b218e790d9f577a7956e11cc5a4d4f540d087e52989613a2b0c307700475
Tx public key: 6f6a500b84bcd7f815afc61cd8d06420c5e8132640af9572e21eea2708e3c13a
Timestamp: 1705468697 Timestamp [UCT]: 2024-01-17 05:18:17 Age [y:d:h:m:s]: 01:356:09:40:36
Block: 937054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513638 RingCT/type: yes/0
Extra: 016f6a500b84bcd7f815afc61cd8d06420c5e8132640af9572e21eea2708e3c13a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd2e23675c10c770ce38f0c19e1e6d4eaede3e6b3a07cd311fa9cd7f3a93fafe 0.600000000000 1395098 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": 937064, "vin": [ { "gen": { "height": 937054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd2e23675c10c770ce38f0c19e1e6d4eaede3e6b3a07cd311fa9cd7f3a93fafe" } } ], "extra": [ 1, 111, 106, 80, 11, 132, 188, 215, 248, 21, 175, 198, 28, 216, 208, 100, 32, 197, 232, 19, 38, 64, 175, 149, 114, 226, 30, 234, 39, 8, 227, 193, 58, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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