Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad25a0548d24cbc8d9fc52621f5f46f93bfeec6cc1419310404ca1786693c530

Tx prefix hash: 505dd5ccac9a277734416be0832158b2a7d9b88e99dc6f53080c33f08e970bc9
Tx public key: 8afece4d66a978e2663f16b6f389dd4e216fa9e35a1279e74cdede45c09022f0
Timestamp: 1733025708 Timestamp [UCT]: 2024-12-01 04:01:48 Age [y:d:h:m:s]: 00:114:19:21:06
Block: 1165448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81840 RingCT/type: yes/0
Extra: 018afece4d66a978e2663f16b6f389dd4e216fa9e35a1279e74cdede45c09022f00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94a5c2d3c7bad5518be862f87905e9b7ba0da8657c404dc4ed164c7085d23fd6 0.600000000000 1651123 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": 1165458, "vin": [ { "gen": { "height": 1165448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94a5c2d3c7bad5518be862f87905e9b7ba0da8657c404dc4ed164c7085d23fd6" } } ], "extra": [ 1, 138, 254, 206, 77, 102, 169, 120, 226, 102, 63, 22, 182, 243, 137, 221, 78, 33, 111, 169, 227, 90, 18, 121, 231, 76, 222, 222, 69, 192, 144, 34, 240, 2, 17, 0, 0, 0, 2, 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