Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7774cfd59547d7861a051658809a59aca2545848fe91d5dabc4ecd9668df06a5

Tx prefix hash: 6f6799a7321861f1ad00f83991e5aaafbb47d6189fed0afe870c322099ab92cf
Tx public key: a6c5e0b417f7f23889b93102f523ef300c819c819266cee3e30b7c3ff786f798
Timestamp: 1635964197 Timestamp [UCT]: 2021-11-03 18:29:57 Age [y:d:h:m:s]: 03:131:20:47:15
Block: 366645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 872559 RingCT/type: yes/0
Extra: 01a6c5e0b417f7f23889b93102f523ef300c819c819266cee3e30b7c3ff786f79802110000000137cb3088000000000000000000

1 output(s) for total of 37.424917837000 dcy

stealth address amount amount idx
00: 20179e6e19062f7f6ebbdd445d8547b44e1e1e7947ad828126903c058e2a4dcb 37.424917837000 744195 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": 366655, "vin": [ { "gen": { "height": 366645 } } ], "vout": [ { "amount": 37424917837, "target": { "key": "20179e6e19062f7f6ebbdd445d8547b44e1e1e7947ad828126903c058e2a4dcb" } } ], "extra": [ 1, 166, 197, 224, 180, 23, 247, 242, 56, 137, 185, 49, 2, 245, 35, 239, 48, 12, 129, 156, 129, 146, 102, 206, 227, 227, 11, 124, 63, 247, 134, 247, 152, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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