Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a1e5fe15a4e70436dc0bcc40f7175ac438cb4acbc1783cdc38281d807f59c68

Tx prefix hash: 8de2488f0d5a6f1816a024873d075e08304b273bafbf422b4ad8b3df45113eb7
Tx public key: f83e048712b4558928170965f6cc3a6d434d354dbfc93a38c42a17ef94e93315
Timestamp: 1702779348 Timestamp [UCT]: 2023-12-17 02:15:48 Age [y:d:h:m:s]: 01:035:18:36:01
Block: 914785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286887 RingCT/type: yes/0
Extra: 01f83e048712b4558928170965f6cc3a6d434d354dbfc93a38c42a17ef94e93315021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78dcc849b5cfc790c477d7716ff1db41d64f7704f428ee8f4cc5b11d72d1c4ca 0.600000000000 1372137 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": 914795, "vin": [ { "gen": { "height": 914785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78dcc849b5cfc790c477d7716ff1db41d64f7704f428ee8f4cc5b11d72d1c4ca" } } ], "extra": [ 1, 248, 62, 4, 135, 18, 180, 85, 137, 40, 23, 9, 101, 246, 204, 58, 109, 67, 77, 53, 77, 191, 201, 58, 56, 196, 42, 23, 239, 148, 233, 51, 21, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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