Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a03ce9bb39884b5480f00fba783192f4a3b4cad7523a242a350988587775d4e

Tx prefix hash: e27690318d26b16cb0d036f5d4159ab7f1ef1061a76b4a6c55525238e81f699f
Tx public key: 04a037d7aedc54f006ab48cca2594466aecaac9d9ad4dfb1847dfb200e4d93f1
Timestamp: 1711785516 Timestamp [UCT]: 2024-03-30 07:58:36 Age [y:d:h:m:s]: 01:047:18:38:09
Block: 989476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295111 RingCT/type: yes/0
Extra: 0104a037d7aedc54f006ab48cca2594466aecaac9d9ad4dfb1847dfb200e4d93f102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bc6073187ee691bc03908664b1053dd63e12bda1a0465c9d6f66ccc0975f74b 0.600000000000 1449773 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": 989486, "vin": [ { "gen": { "height": 989476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bc6073187ee691bc03908664b1053dd63e12bda1a0465c9d6f66ccc0975f74b" } } ], "extra": [ 1, 4, 160, 55, 215, 174, 220, 84, 240, 6, 171, 72, 204, 162, 89, 68, 102, 174, 202, 172, 157, 154, 212, 223, 177, 132, 125, 251, 32, 14, 77, 147, 241, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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