Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bd652c369a2a44739115eb3aa19317121510114c28314896aac6d3f93434b6e

Tx prefix hash: 69da22eb05ce17c73ae0f92c6f38b8bf0a8fbf259dbebc4eb9285aea633264f4
Tx public key: f32bd6741b67508b3c04218b92cde775d659f59d1f12f3f73703d14e8bfac64f
Timestamp: 1583858040 Timestamp [UCT]: 2020-03-10 16:34:00 Age [y:d:h:m:s]: 04:240:19:07:05
Block: 80016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1067049 RingCT/type: yes/0
Extra: 01f32bd6741b67508b3c04218b92cde775d659f59d1f12f3f73703d14e8bfac64f021100000001203e3db0000000000000000000

1 output(s) for total of 333.330125404000 dcy

stealth address amount amount idx
00: 2765e1b37d25ffb6e21efc272913d2f8938105049cc8299aaf4d4250a6ffed4e 333.330125404000 146402 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": 80026, "vin": [ { "gen": { "height": 80016 } } ], "vout": [ { "amount": 333330125404, "target": { "key": "2765e1b37d25ffb6e21efc272913d2f8938105049cc8299aaf4d4250a6ffed4e" } } ], "extra": [ 1, 243, 43, 214, 116, 27, 103, 80, 139, 60, 4, 33, 139, 146, 205, 231, 117, 214, 89, 245, 157, 31, 18, 243, 247, 55, 3, 209, 78, 139, 250, 198, 79, 2, 17, 0, 0, 0, 1, 32, 62, 61, 176, 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