Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070634e2f938495389bdeee5a0bdca588e5d17bc2b59e3b3edb8c8563bf40a54

Tx prefix hash: 70033bfdea39b0e6ec7f697b63b9f6b36fbb2021bd1e8d736cebdad2087612db
Tx public key: 69881df9a64537371edf2ed2067369b24016eee5339bf3e317ae226abe6fb6bc
Timestamp: 1635938699 Timestamp [UCT]: 2021-11-03 11:24:59 Age [y:d:h:m:s]: 03:068:00:18:58
Block: 366434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827141 RingCT/type: yes/0
Extra: 0169881df9a64537371edf2ed2067369b24016eee5339bf3e317ae226abe6fb6bc02110000000df56b629f000000000000000000

1 output(s) for total of 37.484562256000 dcy

stealth address amount amount idx
00: 4adc5ea3f57de597cf87a78ac4cda83314029e0806b31ddcf2f6e6eab9d50e73 37.484562256000 743838 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": 366444, "vin": [ { "gen": { "height": 366434 } } ], "vout": [ { "amount": 37484562256, "target": { "key": "4adc5ea3f57de597cf87a78ac4cda83314029e0806b31ddcf2f6e6eab9d50e73" } } ], "extra": [ 1, 105, 136, 29, 249, 166, 69, 55, 55, 30, 223, 46, 210, 6, 115, 105, 178, 64, 22, 238, 229, 51, 155, 243, 227, 23, 174, 34, 106, 190, 111, 182, 188, 2, 17, 0, 0, 0, 13, 245, 107, 98, 159, 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