Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f68037ee1707cd3ae7dfae0fb57d7a9278ef0c52536b338cfa78d8ab653492

Tx prefix hash: 9e05b75672fc29295e664b0ed97fb11876dc4826bfae41e234ca7298d123c778
Tx public key: a1fa50bc840c1897d9acff565b02fc32914cd048e493f008d780e396a266b99a
Timestamp: 1722369318 Timestamp [UCT]: 2024-07-30 19:55:18 Age [y:d:h:m:s]: 00:209:11:19:43
Block: 1077192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149580 RingCT/type: yes/0
Extra: 01a1fa50bc840c1897d9acff565b02fc32914cd048e493f008d780e396a266b99a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20e5aaa48dd2976f0e3a0d4db407649307b9fc59e5fdc02cb2cc4bb0e98a36d6 0.600000000000 1549739 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": 1077202, "vin": [ { "gen": { "height": 1077192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20e5aaa48dd2976f0e3a0d4db407649307b9fc59e5fdc02cb2cc4bb0e98a36d6" } } ], "extra": [ 1, 161, 250, 80, 188, 132, 12, 24, 151, 217, 172, 255, 86, 91, 2, 252, 50, 145, 76, 208, 72, 228, 147, 240, 8, 215, 128, 227, 150, 162, 102, 185, 154, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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