Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25c8b31b687b7cd79d02d288802542fab53416d4636d5d9302a8ce1658e60e8e

Tx prefix hash: dbaa1a2681c469b125d78f16ccad06a51b507818d3273e1f79bab3f64c55ac33
Tx public key: fe09f2ce30e9235e25c9ac1cc2115b504b4c74f76a8da170d075c940fb100539
Timestamp: 1625676972 Timestamp [UCT]: 2021-07-07 16:56:12 Age [y:d:h:m:s]: 03:341:12:44:07
Block: 289845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1014098 RingCT/type: yes/0
Extra: 01fe09f2ce30e9235e25c9ac1cc2115b504b4c74f76a8da170d075c940fb1005390211000000033634f08d000000000000000000

1 output(s) for total of 67.240549960000 dcy

stealth address amount amount idx
00: 647ece845776d736b13e06d2867dd236fd7afa2e5c0b7c41920ae0f1e17bf469 67.240549960000 607169 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": 289855, "vin": [ { "gen": { "height": 289845 } } ], "vout": [ { "amount": 67240549960, "target": { "key": "647ece845776d736b13e06d2867dd236fd7afa2e5c0b7c41920ae0f1e17bf469" } } ], "extra": [ 1, 254, 9, 242, 206, 48, 233, 35, 94, 37, 201, 172, 28, 194, 17, 91, 80, 75, 76, 116, 247, 106, 141, 161, 112, 208, 117, 201, 64, 251, 16, 5, 57, 2, 17, 0, 0, 0, 3, 54, 52, 240, 141, 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