Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 578efc424cac96b2f36c123de8c82bc769033771245318c8156101fee3e8efa3

Tx prefix hash: c65448877916f3823ef7ef8767675a2688048e332d9a99a2b989e6cecc2dbde9
Tx public key: 1267f60df87db10a8a4fbc63f8bfa641cf28b83980238bc9ad3cc93558238c6b
Timestamp: 1580588840 Timestamp [UCT]: 2020-02-01 20:27:20 Age [y:d:h:m:s]: 04:328:23:51:45
Block: 56749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126354 RingCT/type: yes/0
Extra: 011267f60df87db10a8a4fbc63f8bfa641cf28b83980238bc9ad3cc93558238c6b0211000000084943cd9f000000000000000000

1 output(s) for total of 398.084550782000 dcy

stealth address amount amount idx
00: 9ecd6b2b2178d2c02ea586da5e084a02922a98fc4351777a54196f4cd8f33f69 398.084550782000 104628 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": 56759, "vin": [ { "gen": { "height": 56749 } } ], "vout": [ { "amount": 398084550782, "target": { "key": "9ecd6b2b2178d2c02ea586da5e084a02922a98fc4351777a54196f4cd8f33f69" } } ], "extra": [ 1, 18, 103, 246, 13, 248, 125, 177, 10, 138, 79, 188, 99, 248, 191, 166, 65, 207, 40, 184, 57, 128, 35, 139, 201, 173, 60, 201, 53, 88, 35, 140, 107, 2, 17, 0, 0, 0, 8, 73, 67, 205, 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