Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c8062d95a7e728adf387a086a014b9cb2eef2ff34cd7aaa740d2d8dc6af198c

Tx prefix hash: c04795704bf6fb2ae200179e8c7039458b5ebf3c5bee8dbe7738e6fc381a0a59
Tx public key: 00475732198624e0703a632ddb2872173c59cf209a0c9e3874d5267eb447974d
Timestamp: 1736349044 Timestamp [UCT]: 2025-01-08 15:10:44 Age [y:d:h:m:s]: 01:017:02:54:56
Block: 1192951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270530 RingCT/type: yes/0
Extra: 0100475732198624e0703a632ddb2872173c59cf209a0c9e3874d5267eb447974d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a09c7d8b16d490426563eb65c7fff1b001f24e8c8a76f68145f214d2b2d586fb 0.600000000000 1679508 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": 1192961, "vin": [ { "gen": { "height": 1192951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a09c7d8b16d490426563eb65c7fff1b001f24e8c8a76f68145f214d2b2d586fb" } } ], "extra": [ 1, 0, 71, 87, 50, 25, 134, 36, 224, 112, 58, 99, 45, 219, 40, 114, 23, 60, 89, 207, 32, 154, 12, 158, 56, 116, 213, 38, 126, 180, 71, 151, 77, 2, 17, 0, 0, 0, 1, 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