Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48eb9ec6869a42ca2d049c4daa7060b5b924892c57ce396874d63ef5ab12784b

Tx prefix hash: 1f0ff3e045074d944b2ed4f8fa520a1c5745fa047606f171b21d61dc71751cf1
Tx public key: f2474a8fcc377b29c23e25e1331484d0fc47bea6c0b67d7e817fbfa85cc54f98
Timestamp: 1582035729 Timestamp [UCT]: 2020-02-18 14:22:09 Age [y:d:h:m:s]: 05:260:22:43:38
Block: 67522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1337279 RingCT/type: yes/0
Extra: 01f2474a8fcc377b29c23e25e1331484d0fc47bea6c0b67d7e817fbfa85cc54f980211000000010aca7173000000000000000000

1 output(s) for total of 366.683868153000 dcy

stealth address amount amount idx
00: eb2e968d265f316c1ff01457f748b2ddad2342ff9e79bf9b2bae005a63da1393 366.683868153000 124385 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": 67532, "vin": [ { "gen": { "height": 67522 } } ], "vout": [ { "amount": 366683868153, "target": { "key": "eb2e968d265f316c1ff01457f748b2ddad2342ff9e79bf9b2bae005a63da1393" } } ], "extra": [ 1, 242, 71, 74, 143, 204, 55, 123, 41, 194, 62, 37, 225, 51, 20, 132, 208, 252, 71, 190, 166, 192, 182, 125, 126, 129, 127, 191, 168, 92, 197, 79, 152, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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