Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72b29cd626e9fbc51cdaef437e8103d1827e90d81dfcfc3cc298b4595ccf096b

Tx prefix hash: 813c84686fb7fe84700868e85d5721f55926753a1c8eb48fdf77e2b1bac7588d
Tx public key: 248d71b7e63748cc9a1dfb80e01f3e9e1c72270a4fc077f1d74c527ce769d2f4
Timestamp: 1577729513 Timestamp [UCT]: 2019-12-30 18:11:53 Age [y:d:h:m:s]: 05:305:10:04:44
Block: 35226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1365735 RingCT/type: yes/0
Extra: 01248d71b7e63748cc9a1dfb80e01f3e9e1c72270a4fc077f1d74c527ce769d2f40211000000024ac5aa02000000000000000000

1 output(s) for total of 469.118428323000 dcy

stealth address amount amount idx
00: 227d1f70cdd40c0efb6458e636500ba61ad02c33bb26521ee306e8621a6e7f65 469.118428323000 59328 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": 35236, "vin": [ { "gen": { "height": 35226 } } ], "vout": [ { "amount": 469118428323, "target": { "key": "227d1f70cdd40c0efb6458e636500ba61ad02c33bb26521ee306e8621a6e7f65" } } ], "extra": [ 1, 36, 141, 113, 183, 230, 55, 72, 204, 154, 29, 251, 128, 224, 31, 62, 158, 28, 114, 39, 10, 79, 192, 119, 241, 215, 76, 82, 124, 231, 105, 210, 244, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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