Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d33f9dff5f7ea39b909c9cddec5a845ac3c03308cd57df0df421b272e8014ed

Tx prefix hash: bfeb0e2c4abab450ac91c60982bf144ce682d3f85030e2e90a2342d3f2135c02
Tx public key: 0e87f87bd9d7442c21db6f0c565a119ef05f7559471983f2778fb3b4949d8218
Timestamp: 1739249941 Timestamp [UCT]: 2025-02-11 04:59:01 Age [y:d:h:m:s]: 00:323:00:45:02
Block: 1216710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228681 RingCT/type: yes/0
Extra: 010e87f87bd9d7442c21db6f0c565a119ef05f7559471983f2778fb3b4949d82180211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3cd3043b7c09830950ea5861952d264a1d957ee4977c2e08a188baed3d34bf0 0.600000000000 1703517 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": 1216720, "vin": [ { "gen": { "height": 1216710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3cd3043b7c09830950ea5861952d264a1d957ee4977c2e08a188baed3d34bf0" } } ], "extra": [ 1, 14, 135, 248, 123, 217, 215, 68, 44, 33, 219, 111, 12, 86, 90, 17, 158, 240, 95, 117, 89, 71, 25, 131, 242, 119, 143, 179, 180, 148, 157, 130, 24, 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