Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 948f4fd4f48642602f66b18b575d9e8ff3b212bc622f0377e1e16d639f61ae4c

Tx prefix hash: b9514da4237d05ca8fc68177ff5d1de892e7bce6d01674d3fa95a341f536ff72
Tx public key: 7f4d115a1383328926f44465b67685d92fc839c3b3e2a54d220b2a39e5c355bc
Timestamp: 1735833409 Timestamp [UCT]: 2025-01-02 15:56:49 Age [y:d:h:m:s]: 00:349:09:45:04
Block: 1188686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247279 RingCT/type: yes/0
Extra: 017f4d115a1383328926f44465b67685d92fc839c3b3e2a54d220b2a39e5c355bc021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f0c9208a9a2119ee9c130b3aafa85612092db812db294f5d86ddd8c7f1bbfdb 0.600000000000 1675189 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": 1188696, "vin": [ { "gen": { "height": 1188686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f0c9208a9a2119ee9c130b3aafa85612092db812db294f5d86ddd8c7f1bbfdb" } } ], "extra": [ 1, 127, 77, 17, 90, 19, 131, 50, 137, 38, 244, 68, 101, 182, 118, 133, 217, 47, 200, 57, 195, 179, 226, 165, 77, 34, 11, 42, 57, 229, 195, 85, 188, 2, 17, 0, 0, 0, 2, 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