Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1d82e09449abe7d25152027f222c93c4620bf5345585f9a98e89383da54bd1a

Tx prefix hash: 33a1de2795c26e62dc5804fea57679d0eb8767204b83c1fe815f156b4db2ec1c
Tx public key: 07294b69ae15577742dcfce742a4690737e2c5202a4e8af709174f8dfc9c1ec4
Timestamp: 1649764065 Timestamp [UCT]: 2022-04-12 11:47:45 Age [y:d:h:m:s]: 03:034:10:14:00
Block: 478586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 805145 RingCT/type: yes/0
Extra: 0107294b69ae15577742dcfce742a4690737e2c5202a4e8af709174f8dfc9c1ec40211000000022e6b1fd5000000000000000000

1 output(s) for total of 15.931114111000 dcy

stealth address amount amount idx
00: 3e287c096ce6549a1b8ccbcb693f13c78cd54975889d0bf1f3b9a96cdd7bf7fa 15.931114111000 899365 of 0

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": 478596, "vin": [ { "gen": { "height": 478586 } } ], "vout": [ { "amount": 15931114111, "target": { "key": "3e287c096ce6549a1b8ccbcb693f13c78cd54975889d0bf1f3b9a96cdd7bf7fa" } } ], "extra": [ 1, 7, 41, 75, 105, 174, 21, 87, 119, 66, 220, 252, 231, 66, 164, 105, 7, 55, 226, 197, 32, 42, 78, 138, 247, 9, 23, 79, 141, 252, 156, 30, 196, 2, 17, 0, 0, 0, 2, 46, 107, 31, 213, 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