Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f748552dd18c53167e10e9e7fb862536e1771bf5a6083cad3024b6da163d3448

Tx prefix hash: 01ad09f4b2a42cc85e2e5a076a3f560c32fa9a71b9d68e098219f9471a3e8ad6
Tx public key: 38419ca6137f7936cb62737bca411de81bdadc72daf66615d75d0c551e2183f7
Timestamp: 1714468972 Timestamp [UCT]: 2024-04-30 09:22:52 Age [y:d:h:m:s]: 00:339:06:39:43
Block: 1011704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242531 RingCT/type: yes/0
Extra: 0138419ca6137f7936cb62737bca411de81bdadc72daf66615d75d0c551e2183f70211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a90452ab62597c7a8bc1a174fdc67ba6fb7137dc0a23588fd6d8de6ca5e8ad3 0.600000000000 1473998 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": 1011714, "vin": [ { "gen": { "height": 1011704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a90452ab62597c7a8bc1a174fdc67ba6fb7137dc0a23588fd6d8de6ca5e8ad3" } } ], "extra": [ 1, 56, 65, 156, 166, 19, 127, 121, 54, 203, 98, 115, 123, 202, 65, 29, 232, 27, 218, 220, 114, 218, 246, 102, 21, 215, 93, 12, 85, 30, 33, 131, 247, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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