Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af6f37d4ee41bdb211386fd7360b02f2462f3829b99014c5efd93176f3dd187

Tx prefix hash: e719411d33d4c931b22da55eabfdce8afbc952154d6389083a422aca0243661a
Tx public key: 4c99099458ca786f03823854b694e2e26cdaf0413a95a4f76a0c8deeedd0b726
Timestamp: 1726001964 Timestamp [UCT]: 2024-09-10 20:59:24 Age [y:d:h:m:s]: 01:054:10:55:05
Block: 1107316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297333 RingCT/type: yes/0
Extra: 014c99099458ca786f03823854b694e2e26cdaf0413a95a4f76a0c8deeedd0b726021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e4ea802a2bba458f5ba170ee19e999a3d2e4ec74d6c94b8dd078c5b1319b4a1 0.600000000000 1584927 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": 1107326, "vin": [ { "gen": { "height": 1107316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e4ea802a2bba458f5ba170ee19e999a3d2e4ec74d6c94b8dd078c5b1319b4a1" } } ], "extra": [ 1, 76, 153, 9, 148, 88, 202, 120, 111, 3, 130, 56, 84, 182, 148, 226, 226, 108, 218, 240, 65, 58, 149, 164, 247, 106, 12, 141, 238, 237, 208, 183, 38, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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