Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be865c5d653215bd141372305c3e7fab4dd24eee0b2e889924f799611b7c91d7

Tx prefix hash: 2c3b28aab4ed6ba68ca609c8ebd8a0d00c1ee687ebf1f30f67a1acd394d139c7
Tx public key: 7d6d87b46726c9e99560118cefdef0fbf8fd3e86dc6888a2be634295ab470916
Timestamp: 1721061257 Timestamp [UCT]: 2024-07-15 16:34:17 Age [y:d:h:m:s]: 00:252:10:28:47
Block: 1066368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180316 RingCT/type: yes/0
Extra: 017d6d87b46726c9e99560118cefdef0fbf8fd3e86dc6888a2be634295ab470916021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2ccdbdf7f4e335140a33f79684aaf904748b1479ebde79efe379952148efff2 0.600000000000 1536941 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": 1066378, "vin": [ { "gen": { "height": 1066368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2ccdbdf7f4e335140a33f79684aaf904748b1479ebde79efe379952148efff2" } } ], "extra": [ 1, 125, 109, 135, 180, 103, 38, 201, 233, 149, 96, 17, 140, 239, 222, 240, 251, 248, 253, 62, 134, 220, 104, 136, 162, 190, 99, 66, 149, 171, 71, 9, 22, 2, 17, 0, 0, 0, 3, 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