Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee73af0d334700310dc02b2d69d5e011859af4a64646e9cb011d6b6dfa9a4722

Tx prefix hash: 8c529bf152b47726b925d19544b183c7a0fe3db0503fa4090d42b1f9f2a869ab
Tx public key: 3174ce56f810465eb43502b1e817651851a0a136eb6414f1e832a8a853c89ceb
Timestamp: 1740621005 Timestamp [UCT]: 2025-02-27 01:50:05 Age [y:d:h:m:s]: 00:272:11:32:18
Block: 1228041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192522 RingCT/type: yes/0
Extra: 013174ce56f810465eb43502b1e817651851a0a136eb6414f1e832a8a853c89ceb0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c978e5a6c1d9846e822141d43269a4c1716eaa4a0d6ee285edefc24fd7bfe13 0.600000000000 1714918 of 15

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": 1228051, "vin": [ { "gen": { "height": 1228041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c978e5a6c1d9846e822141d43269a4c1716eaa4a0d6ee285edefc24fd7bfe13" } } ], "extra": [ 1, 49, 116, 206, 86, 248, 16, 70, 94, 180, 53, 2, 177, 232, 23, 101, 24, 81, 160, 161, 54, 235, 100, 20, 241, 232, 50, 168, 168, 83, 200, 156, 235, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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