Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebe6f1419d7e4c393a5c46b467d1937b8e1fcba21ce0e274d1d1b9e75a190db9

Tx prefix hash: 1145ab9c92a975a6e641fa09bb54cd6135ea7c986c8deaee80c97e2f842bf7ec
Tx public key: aea667432d6166f4ab0aa2d8072066631c578e31490ec693271cba65e4ca67ed
Timestamp: 1578319716 Timestamp [UCT]: 2020-01-06 14:08:36 Age [y:d:h:m:s]: 04:357:23:52:35
Block: 39715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145331 RingCT/type: yes/0
Extra: 01aea667432d6166f4ab0aa2d8072066631c578e31490ec693271cba65e4ca67ed0211000000cedcee4b4d000000000000000000

1 output(s) for total of 453.333677988000 dcy

stealth address amount amount idx
00: 10b7975802aa69928fb41a08079d2aaf7334243759422ce81aba5534896c2429 453.333677988000 68911 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": 39725, "vin": [ { "gen": { "height": 39715 } } ], "vout": [ { "amount": 453333677988, "target": { "key": "10b7975802aa69928fb41a08079d2aaf7334243759422ce81aba5534896c2429" } } ], "extra": [ 1, 174, 166, 103, 67, 45, 97, 102, 244, 171, 10, 162, 216, 7, 32, 102, 99, 28, 87, 142, 49, 73, 14, 198, 147, 39, 28, 186, 101, 228, 202, 103, 237, 2, 17, 0, 0, 0, 206, 220, 238, 75, 77, 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