Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0733c82a5057c51a222724135569e53da2c265c3d59695a15f560b7bd396a880

Tx prefix hash: 4910d6e769cb3bba4c07699ada42243b43fbfd9da53879219a9452a2fc55bec7
Tx public key: ca0165b420b1e9aa1c187a50c928ecd4156300f9cf6e1d3097b5dedcc4a991a1
Timestamp: 1720884621 Timestamp [UCT]: 2024-07-13 15:30:21 Age [y:d:h:m:s]: 00:270:03:03:15
Block: 1064898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192980 RingCT/type: yes/0
Extra: 01ca0165b420b1e9aa1c187a50c928ecd4156300f9cf6e1d3097b5dedcc4a991a102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb6e639ded2ad409b81d00aac04e13f8fdc8133cbb63b30a7e38f8f8716fefb0 0.600000000000 1535439 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": 1064908, "vin": [ { "gen": { "height": 1064898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb6e639ded2ad409b81d00aac04e13f8fdc8133cbb63b30a7e38f8f8716fefb0" } } ], "extra": [ 1, 202, 1, 101, 180, 32, 177, 233, 170, 28, 24, 122, 80, 201, 40, 236, 212, 21, 99, 0, 249, 207, 110, 29, 48, 151, 181, 222, 220, 196, 169, 145, 161, 2, 17, 0, 0, 0, 1, 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