Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c146264aee0868f5a0f404223ad8e8f006c68eb1663a4b8331fadbc88bb9338

Tx prefix hash: 0c2c7f760704edfd276338615c2f485881379c63c2ad27e356ca61304917d84c
Tx public key: 639061b609303136cc9a8e03d09b484c3500783c048c94bd5f15b7c9ae2ef0fd
Timestamp: 1722717280 Timestamp [UCT]: 2024-08-03 20:34:40 Age [y:d:h:m:s]: 01:092:08:04:04
Block: 1080076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324477 RingCT/type: yes/0
Extra: 01639061b609303136cc9a8e03d09b484c3500783c048c94bd5f15b7c9ae2ef0fd021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ec232da8691c5495e4cbf2765573e24f2cf4e6f5dd94f93c6378bcd35b51c1c 0.600000000000 1553299 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": 1080086, "vin": [ { "gen": { "height": 1080076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ec232da8691c5495e4cbf2765573e24f2cf4e6f5dd94f93c6378bcd35b51c1c" } } ], "extra": [ 1, 99, 144, 97, 182, 9, 48, 49, 54, 204, 154, 142, 3, 208, 155, 72, 76, 53, 0, 120, 60, 4, 140, 148, 189, 95, 21, 183, 201, 174, 46, 240, 253, 2, 17, 0, 0, 0, 5, 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