Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e42acaefb0cd4b3a8d8ca4b47b8183ffa99373ae1c3215ef5ea3cdec9e8dd536

Tx prefix hash: abd27b1363d38e9ca86e27bf4e61508920a4a179ce6dfc76ed1fbe0a816efbbc
Tx public key: 2a03e06b0e0f45aa2a46b1372ec46eea0ea91daeab49fadd9bbf6a918385163e
Timestamp: 1577920128 Timestamp [UCT]: 2020-01-01 23:08:48 Age [y:d:h:m:s]: 05:098:06:48:03
Block: 36692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220082 RingCT/type: yes/0
Extra: 012a03e06b0e0f45aa2a46b1372ec46eea0ea91daeab49fadd9bbf6a918385163e02110000000fd81c26c0000000000000000000

1 output(s) for total of 463.900696861000 dcy

stealth address amount amount idx
00: 0c384a0ed5407da86d804d6e6203319aa0ce6ea407fa3f4546cd7df16b386a8a 463.900696861000 62202 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": 36702, "vin": [ { "gen": { "height": 36692 } } ], "vout": [ { "amount": 463900696861, "target": { "key": "0c384a0ed5407da86d804d6e6203319aa0ce6ea407fa3f4546cd7df16b386a8a" } } ], "extra": [ 1, 42, 3, 224, 107, 14, 15, 69, 170, 42, 70, 177, 55, 46, 196, 110, 234, 14, 169, 29, 174, 171, 73, 250, 221, 155, 191, 106, 145, 131, 133, 22, 62, 2, 17, 0, 0, 0, 15, 216, 28, 38, 192, 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