Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1001c447b64eff3891fe49df3d6dcf1ef217b69e1113016acaf37a261e2d87b

Tx prefix hash: d73c8fee7075018391849fa096c512d72e900d95052158053e03dc0ab866fff0
Tx public key: c3a0c6b3ac76de395b0d03892c73aecfcb83ae5077653a8b338bdf1ecb3c2ddd
Timestamp: 1650142154 Timestamp [UCT]: 2022-04-16 20:49:14 Age [y:d:h:m:s]: 03:026:12:53:57
Block: 481655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 799568 RingCT/type: yes/0
Extra: 01c3a0c6b3ac76de395b0d03892c73aecfcb83ae5077653a8b338bdf1ecb3c2ddd021100000001bf7ee4e7000000000000000000

1 output(s) for total of 15.562425052000 dcy

stealth address amount amount idx
00: e32e4c27bc15a5ef0d75191e20dc8d8debde47fc9e27a6f2e5848fdf8c844cf7 15.562425052000 902976 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": 481665, "vin": [ { "gen": { "height": 481655 } } ], "vout": [ { "amount": 15562425052, "target": { "key": "e32e4c27bc15a5ef0d75191e20dc8d8debde47fc9e27a6f2e5848fdf8c844cf7" } } ], "extra": [ 1, 195, 160, 198, 179, 172, 118, 222, 57, 91, 13, 3, 137, 44, 115, 174, 207, 203, 131, 174, 80, 119, 101, 58, 139, 51, 139, 223, 30, 203, 60, 45, 221, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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