Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a4f4093f2dc3549c6e9e0499a3d63ea9ce9658780650659e4c24db71e37e00

Tx prefix hash: c5bbdeeae3532a90bffd547a005366c1f9339f74af30ca041c2df3cd0952d73b
Tx public key: 7ea3db369b69f390eb49c8df272594ac4d717ff6b62ab5a67d3f33f39e10527e
Timestamp: 1588737175 Timestamp [UCT]: 2020-05-06 03:52:55 Age [y:d:h:m:s]: 05:179:17:58:31
Block: 99097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1303107 RingCT/type: yes/0
Extra: 017ea3db369b69f390eb49c8df272594ac4d717ff6b62ab5a67d3f33f39e10527e0211000001596fa03929000000000000000000

1 output(s) for total of 288.171657914000 dcy

stealth address amount amount idx
00: a5ea1efe53833edcabda7f61d6eaec5d512a732e379a3c5b49893079722d6a48 288.171657914000 174937 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": 99107, "vin": [ { "gen": { "height": 99097 } } ], "vout": [ { "amount": 288171657914, "target": { "key": "a5ea1efe53833edcabda7f61d6eaec5d512a732e379a3c5b49893079722d6a48" } } ], "extra": [ 1, 126, 163, 219, 54, 155, 105, 243, 144, 235, 73, 200, 223, 39, 37, 148, 172, 77, 113, 127, 246, 182, 42, 181, 166, 125, 63, 51, 243, 158, 16, 82, 126, 2, 17, 0, 0, 1, 89, 111, 160, 57, 41, 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