Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e2db0e8728e3af1ee0fea3717896a392853a8add1f00e0c67f66b8016240b1f

Tx prefix hash: d6e8369407e2d84e2357205d88691819324e20c1f6bd3126f2b4cf8d38f8390b
Tx public key: 0e287e76799694af6b268c4f07ec8b7d828421401939298386226f947fabe945
Timestamp: 1578553002 Timestamp [UCT]: 2020-01-09 06:56:42 Age [y:d:h:m:s]: 05:025:23:50:58
Block: 41836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168480 RingCT/type: yes/0
Extra: 010e287e76799694af6b268c4f07ec8b7d828421401939298386226f947fabe9450211000000104ac5aa02000000000000000000

1 output(s) for total of 446.047192301000 dcy

stealth address amount amount idx
00: 5e6369fb68c5150646228d39272d36a41bf15a244df3c4868b14724b27f1c08b 446.047192301000 74972 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": 41846, "vin": [ { "gen": { "height": 41836 } } ], "vout": [ { "amount": 446047192301, "target": { "key": "5e6369fb68c5150646228d39272d36a41bf15a244df3c4868b14724b27f1c08b" } } ], "extra": [ 1, 14, 40, 126, 118, 121, 150, 148, 175, 107, 38, 140, 79, 7, 236, 139, 125, 130, 132, 33, 64, 25, 57, 41, 131, 134, 34, 111, 148, 127, 171, 233, 69, 2, 17, 0, 0, 0, 16, 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