Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d86a4eaa99c78a006dd64263f80e732de84e3dc4eedb58a2f398e7951bbf8be9

Tx prefix hash: d8a7384a0ce4b98c4e7759890ab93aa6638264434b7a42d5fe9bd3df04602c1a
Tx public key: 522be9e8e61ae82eaf3216bbf1db02c7e9ac8fb2b99a7407481c74b7b7722016
Timestamp: 1583095238 Timestamp [UCT]: 2020-03-01 20:40:38 Age [y:d:h:m:s]: 04:259:08:00:05
Block: 75028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1078977 RingCT/type: yes/0
Extra: 01522be9e8e61ae82eaf3216bbf1db02c7e9ac8fb2b99a7407481c74b7b772201602110000012012c4732d000000000000000000

1 output(s) for total of 346.259651531000 dcy

stealth address amount amount idx
00: cf893e82f027c55abbc0c79ce1a31b7396f1028ce51235c96a8bf1217d21d791 346.259651531000 138686 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": 75038, "vin": [ { "gen": { "height": 75028 } } ], "vout": [ { "amount": 346259651531, "target": { "key": "cf893e82f027c55abbc0c79ce1a31b7396f1028ce51235c96a8bf1217d21d791" } } ], "extra": [ 1, 82, 43, 233, 232, 230, 26, 232, 46, 175, 50, 22, 187, 241, 219, 2, 199, 233, 172, 143, 178, 185, 154, 116, 7, 72, 28, 116, 183, 183, 114, 32, 22, 2, 17, 0, 0, 1, 32, 18, 196, 115, 45, 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