Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d75b2a5c4a577bf9ca5f35e82845edfc14cf04d536c1d088b1243407bf32b22

Tx prefix hash: 1ed79c239140ec2e5c1a2521569c29979803e9e6c350c094d25c4e1b2844eec2
Tx public key: 7603191e420b3b88cccdb801d22a9c767595c8e5384ec6b898283019b1d5e55b
Timestamp: 1735695522 Timestamp [UCT]: 2025-01-01 01:38:42 Age [y:d:h:m:s]: 00:093:22:55:30
Block: 1187543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66942 RingCT/type: yes/0
Extra: 017603191e420b3b88cccdb801d22a9c767595c8e5384ec6b898283019b1d5e55b021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 397a7379c26aa1851742f43303b5430a37590e169789cd207066839d19a042e7 0.600000000000 1674034 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": 1187553, "vin": [ { "gen": { "height": 1187543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "397a7379c26aa1851742f43303b5430a37590e169789cd207066839d19a042e7" } } ], "extra": [ 1, 118, 3, 25, 30, 66, 11, 59, 136, 204, 205, 184, 1, 210, 42, 156, 118, 117, 149, 200, 229, 56, 78, 198, 184, 152, 40, 48, 25, 177, 213, 229, 91, 2, 17, 0, 0, 0, 6, 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