Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f8d8f1cf70efb5693820cd8a3dea0a1f7669c84fa9507eda9b2cbce289249d7

Tx prefix hash: 066f148993e9a540f69ba2f67b7b7ae8e73fa6f5d2d06f0297009ba0557343a5
Tx public key: 7d6ec5f90175073ec825e1790e285063ffefd08eaf217d4c79895d90ef500526
Timestamp: 1738195639 Timestamp [UCT]: 2025-01-30 00:07:19 Age [y:d:h:m:s]: 00:320:21:25:07
Block: 1207987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227132 RingCT/type: yes/0
Extra: 017d6ec5f90175073ec825e1790e285063ffefd08eaf217d4c79895d90ef500526021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c44468a3f8df0ab643c79c3e816e36dd50a0fa72d9d2c7d0551cfafec2892737 0.600000000000 1694714 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": 1207997, "vin": [ { "gen": { "height": 1207987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c44468a3f8df0ab643c79c3e816e36dd50a0fa72d9d2c7d0551cfafec2892737" } } ], "extra": [ 1, 125, 110, 197, 249, 1, 117, 7, 62, 200, 37, 225, 121, 14, 40, 80, 99, 255, 239, 208, 142, 175, 33, 125, 76, 121, 137, 93, 144, 239, 80, 5, 38, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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