Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 118179014f63d513798a604042d7ddb15d46436dd5a1440eecddf8563dc966fe

Tx prefix hash: 86556baac2a02262ea307f040f3a3df5e5ba2ff64123fda5f489d17e504f4422
Tx public key: 067f920cc4a1953e8d0987e0cd1d293fde60249d13918c5f5798ad7a9c184538
Timestamp: 1745984776 Timestamp [UCT]: 2025-04-30 03:46:16 Age [y:d:h:m:s]: 00:035:22:38:22
Block: 1272467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25719 RingCT/type: yes/0
Extra: 01067f920cc4a1953e8d0987e0cd1d293fde60249d13918c5f5798ad7a9c1845380211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e254ae4724995e25d405ac851334c7da2b3eee26348ecc0773302d2953bfa18 0.600000000000 1759742 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": 1272477, "vin": [ { "gen": { "height": 1272467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e254ae4724995e25d405ac851334c7da2b3eee26348ecc0773302d2953bfa18" } } ], "extra": [ 1, 6, 127, 146, 12, 196, 161, 149, 62, 141, 9, 135, 224, 205, 29, 41, 63, 222, 96, 36, 157, 19, 145, 140, 95, 87, 152, 173, 122, 156, 24, 69, 56, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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